Communication apparatus, data recording method, and non-transitory computer-readable medium

ABSTRACT

There is provided a communication apparatus that enables acquisition of data to be sent after a Secure Shell (SSH) connection between a wireless unit and a baseband unit is established. A communication apparatus ( 10 ) according to the present disclosure includes a communication unit ( 11 ) that establishes a first Secure Shell (SSH) connection with a wireless apparatus ( 20 ) that performs wireless communication with a communication terminal ( 40 ), and establishes a second SSH connection with a control apparatus ( 30 ) that performs a baseband process related to a signal used in the wireless communication, and a data recording unit ( 12 ) that records data of a management plane received from the wireless apparatus ( 20 ) through the first SSH connection or the data of the management plane received from the control apparatus ( 30 ) through the second SSH connection.

TECHNICAL FIELD

The present disclosure relates to a communication apparatus, a datarecording method, and a program.

BACKGROUND ART

In recent years, wireless access networks in which a baseband unit and awireless unit of a base station are separated and connected viafronthaul have been used. The Open-Radio Access Network (O-RAN)fronthaul specifications specified in the O-RAN alliance specify thefronthaul specifications between an Open Radio Unit (O-RU) correspondingto a wireless unit and a Distributed Unit (O-DU) corresponding to abaseband unit. One purpose of the O-RAN fronthaul specifications is tofacilitate the connection between O-RUs and O-DUs of different vendorsto achieve multivendor wireless access networks.

Non Patent Literature 1 discloses a procedure, an analysis method, andthe like for verifying interconnectivity between an O-DU and an O-RU.Non Patent Literature 1 discloses that a Fronthaul (FH) Protocolanalyzer is connected between the O-DU and the O-RU to analyze data tobe sent between the O-DU and the O-RU with the FH Protocol analyzer.

CITATION LIST Non Patent Literature

-   Non Patent Literature 1: ORAN-WG4.IOT.0-v01.00 O-RAN Fronthaul    Working Group Fronthaul Interoperability Test Specification (JOT)

SUMMARY OF INVENTION Technical Problem

However, the FH Protocol analyzer disclosed in Non Patent Literature 1can only analyze data that can be acquired before a Secure Shell (SSH)connection between the O-DU and the O-RU is established. That is, the FHProtocol analyzer cannot acquire information sent through the SSH afterthe SSH connection between the O-DU and the O-RU is established. Thus,the FH Protocol analyzer has a problem of being unable to analyze datato be sent between the O-DU and the O-RU through the SSH connection.

A purpose of the present disclosure is to provide a communicationapparatus, a data recording method, and a program that enableacquisition of data to be sent in a Secure Shell (SSH) connection afterthe SSH connection between a wireless unit and a baseband unit isestablished.

Solution to Problem

A communication apparatus according to a first aspect of the presentdisclosure includes a communication unit that establishes a first SecureShell (SSH) connection with a wireless apparatus that performs wirelesscommunication with a communication terminal, and establishes a secondSSH connection with a control apparatus that performs a baseband processrelated to a signal used in the wireless communication, and a datarecording unit that records data of a management plane received from thewireless apparatus through the first SSH connection or the data of themanagement plane received from the control apparatus through the secondSSH connection.

A data recording method according to a second aspect of the presentdisclosure includes establishing a first Secure Shell (SSH) connectionwith a wireless apparatus that performs wireless communication with acommunication terminal, establishing a second SSH connection with acontrol apparatus that performs a baseband process related to a signalused in the wireless communication, and recording data of a managementplane received from the wireless apparatus through the first SSHconnection or the data of the management plane received from the controlapparatus through the second SSH connection.

A program according to a third aspect of the present disclosure causes acomputer to execute establishing a first Secure Shell (SSH) connectionwith a wireless apparatus that performs wireless communication with acommunication terminal, establishing a second SSH connection with acontrol apparatus that performs a baseband process related to a signalused in the wireless communication, and recording data of a managementplane received from the wireless apparatus through the first SSHconnection or the data of the management plane received from the controlapparatus through the second SSH connection.

Advantageous Effects of Invention

With the present disclosure, it is possible to provide a communicationapparatus, a data recording method, and a program that enableacquisition of data to be sent after a Secure Shell (SSH) connectionbetween a wireless unit and a baseband unit is established.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a configuration diagram of a communication apparatus accordingto a first example embodiment;

FIG. 2 is a configuration diagram of a communication system according toa second example embodiment;

FIG. 3 is a diagram showing a protocol stack of an M-Plane according tothe second example embodiment;

FIG. 4 is a diagram showing a protocol stack of a C/U-Plane according tothe second example embodiment;

FIG. 5 is a diagram showing a protocol stack of an S-Plane according tothe second example embodiment;

FIG. 6 is a diagram showing a Star-up sequence related to the M-Planeaccording to the second example embodiment;

FIG. 7 is a diagram showing an SSH connection according to the secondexample embodiment;

FIG. 8 is a diagram showing a Yang module according to the secondexample embodiment;

FIG. 9 is a diagram showing a flow defined between an FH-Proxy, and anO-RU and an O-DU according to the second example embodiment;

FIG. 10 is a diagram showing a process flow classified as Type Baccording to the second example embodiment;

FIG. 11 is a configuration diagram of an FH-Proxy according to a thirdexample embodiment;

FIG. 12 is a diagram showing an Ethernet header according to the thirdexample embodiment;

FIG. 13 is a diagram showing an eCPRI Transport header according to thethird example embodiment;

FIG. 14 is a diagram showing a Section Type 1 message of a C-Planeaccording to the third example embodiment;

FIG. 15 is a diagram showing a Section Type 3 message of the C-Planeaccording to the third example embodiment;

FIG. 16 is a diagram showing a Section Type 1 and 3 message of a U-Planeaccording to the third example embodiment;

FIG. 17 is a diagram showing a modified example of the communicationsystem according to the second and third example embodiments; and

FIG. 18 is a configuration diagram of a communication apparatus and anFH-Proxy according to each example embodiment.

DESCRIPTION OF EMBODIMENTS First Example Embodiment

Hereinafter, example embodiments of the present disclosure will bedescribed with reference to the drawings. First, a configuration exampleof a communication apparatus 10 according to a first example embodimentis described with reference to FIG. 1 . The communication apparatus 10may be a computer apparatus that operates by executing a program.

The communication apparatus 10 includes a communication unit 11 and adata recording unit 12. The communication unit 11 and the data recordingunit 12 may be software or modules whose processes are executed by aprocessor executing a program stored in a memory.

The communication unit 11 establishes a first SSH connection with awireless apparatus 20 that performs wireless communication with acommunication terminal 40, and establishes a second SSH connection witha control apparatus 30 that performs a baseband process related tosignals used by the wireless apparatus 20. The communication terminal 40may be, for example, a smartphone terminal, an Internet of Things (IoT)terminal, a Machine Type

Communication (MTC) device, or the like.

The wireless apparatus 20 may be, for example, an O-RU entity(hereinafter, referred to as an O-RU) specified in the O-RAN alliance.The control apparatus 30 may be, for example, an O-DU entity(hereinafter, referred to as an O-DU) specified in the O-RAN alliance.An entity may be referred to as a node or a node apparatus.

It is assumed that, of a public key A and a secret key A generated bythe wireless apparatus 20, the public key A is preinstalled in thecommunication apparatus 10. In addition, it is assumed that thecommunication apparatus 10 generates a public key B and a secret key Band that the public key B is preinstalled in the control apparatus 30.The communication unit 11 authenticates the wireless apparatus 20 withthe public key A to establish the first SSH connection with the wirelessapparatus 20. In addition, the communication unit 11 authenticates thecontrol apparatus 30 with the public key B to establish the second SSHconnection with the control apparatus 30. The establishment of an SSHconnection is not limited to a method with a public key and may beperformed by other methods.

The data recording unit 12 records data of a management plane receivedfrom the wireless apparatus 20 through the first SSH connection. Thedata recording unit 12 further records the data of the management planereceived from the control apparatus 30 through the second SSHconnection.

The communication apparatus 10 terminates the first SSH connection andthe second SSH connection. Thus, the data recording unit 12 can decryptencrypted data received through the first SSH connection or the secondSSH connection. That is, the data recording unit 12 holds data in aformat that allows the header and payload in each layer of the data tobe analyzed.

The management plane handles, for example, data or messages used by thecontrol apparatus 30 or a Network Management System (NMS) to maintain ormonitor the wireless apparatus 20. The data of the management plane isdata that is sent and received in the management plane.

As described above, the communication apparatus 10 according to thefirst example embodiment can establish an SSH connection with each ofthe wireless apparatus 20 and the control apparatus 30. Thus, the dataof the management plane to be generally sent between the wirelessapparatus 20 and the control apparatus 30 through the SSH connection canbe held in a format that allows the header and payload to be analyzed.As the result, the communication apparatus 10 can acquire data to besent after an SSH connection between the wireless apparatus 20 and thecontrol apparatus 30 is established and analyze the acquired data.

Second Example Embodiment

Next, a configuration example of a communication system according to asecond example embodiment is described with reference to FIG. 2 . Thecommunication system shown in FIG. 2 is a system configuration specifiedmainly in the O-RAN alliance. The communication system in FIG. 2includes a Fronthaul (FH)-Proxy entity (hereinafter, referred to as anFH-Proxy) 50, an O-RU 60, and an O-DU 70.

The FH-Proxy 50 corresponds to the communication apparatus 10 in FIG. 1. The O-RU 60 corresponds to the wireless apparatus 20 in FIG. 1 . TheO-DU 70 corresponds to the control apparatus 30 in FIG. 1 .

Between the FH-Proxy 50 and the O-RU 60, a Management (M)-Plane, aControl (C)-Plane, a User (U)-Plane, and a Synchronization (S)-Plane areconfigured. In addition, between the FH-Proxy 50 and the O-DU 70, anM-Plane, a C-Plane, a U-Plane, and an S-Plane are also configured. TheFH-Proxy 50 behaves pseudo as an O-DU to the O-RU 60, and behaves pseudoas an O-RU to the O-DU 70.

The M-Plane is a protocol for transferring monitoring signals used tomonitor or maintain a device. Specifically, a protocol stack of theM-Plane is shown in FIG. 3 . The M-Plane supports a protocol stack fortransmitting signals used in a NETwork CONFigutation protocol (NETCONF)using Ethernet (registered trademark)/IP/Transmission Control Protocol(TCP)/SSH.

The C-Plane is a protocol for transferring control signals. The U-Planeis a protocol for transferring user data. Specifically, a protocol stackof the C-Plane and the U-Plane is shown in FIG. 4 . The C-Plane and theU-Plane support a protocol stack for transmitting signals used inenhanced Common Public Radio Interface (eCPRI) or Radio over Ethernet(RoE) using Ethernet/IP/User Datagram Protocol (UDP). Alternatively, theC-Plane and the U-Plane may support a protocol stack for transmittingsignals used in eCPRI or RoE directly using Ethernet.

The S-Plane is a protocol for achieving synchronization betweenapparatuses. Specifically, a protocol stack of the S-Plane is shown inFIG. 5 . The S-Plane supports a protocol stack for transmitting signalsused in Precision Time Protocol (PTP) and SyncE using Ethernet.

Next, a Start-up sequence related to the M-Plane is described withreference to FIG. 6 . FIG. 6 shows a procedure, for example, from thestart of the O-RU 60 to be managed by the O-DU 70 until the managementof the O-RU 60 by the O-DU 70 becomes possible. Management may berephrased as monitoring. In addition, in NETCONF, the O-DU 70, which isa network apparatus that manages the O-RU 60, corresponds to a NETCONFclient, and the O-RU 60 to be managed corresponds to a NETCONF server.

FIG. 6 shows that processes are performed between the NETCONF clientcorresponding to the O-DU 70 and the NETCONF server corresponding to theO-RU 60. Here, the communication system used in the second exampleembodiment has a configuration in which the FH-Proxy 50 is arrangedbetween the O-DU 70 and the O-RU 60. Thus, FIG. 6 shows Start-upprocesses to be performed among the NETCONF client, the FH-Proxy 50, andthe NETCONF server.

First, the FH-Proxy 50, the O-RU 60, and the O-DU 70 performs processesfrom “Transport Layer Initialization” to “SSH Secure ConnectionEstablished” that are classified as Type A shown in FIG. 6 . Theprocesses classified as Type A are the processes between the O-RU 60 andthe FH-Proxy 50 and the processes between the O-DU 70 and the FH-Proxy50, which are performed independently. In the processes classified asType A, the FH-Proxy 50 operates as the NETCONF client whencommunicating with the O-RU 60 that is the NETCONF server. In addition,the FH-Proxy 50 operates as the NETCONF server when communicating withthe O-DU 70 that is the NETCONF client. As the result of performing theprocesses classified as Type A, SSH connections are established betweenthe FH-Proxy 50 and the O-RU 60 and between the FH-Proxy 50 and the O-DU70 as shown in FIG. 7 .

In addition, by performing the processes classified as Type A, theFH-Proxy 50, the O-RU 60, and the O-DU 70 also perform the configurationof Transport Layer. The configuration of Transport Layer may be, forexample, to configure an IP address or an Ethernet address, which is aTransport Layer address, for each apparatus. The FH-Proxy 50 sets aTransport Layer address for communicating with the O-DU 70 to bedifferent from a Transport Layer address for communicating with the O-RU60.

By performing the processes classified as Type A, the configuration ofTransport Layer and the establishment of the SSH connection areperformed independently in the link between the O-RU 60 and the FH-Proxy50 and the link between the O-DU 70 and the FH-Proxy 50.

Next, the FH-Proxy 50, the O-RU 60, and the O-DU 70 perform processesfrom “NETCONF Capability discovery” to “Configuration the O-RUoperational parameters” that are classified as Type B shown in FIG. 6 .The processes classified as Type B are processes performed between theO-RU 60 that is the NETCONF server and the O-DU 70 that is the NETCONFclient via the FH-Proxy 50.

Each process of the Start-up sequence shown in FIG. 6 is performed usinga message specified in NETCONF. The set of parameters configured in themessage is specified in the Yang module shown in FIG. 8 . In FIG. 8 ,the parameters labeled “A” are the parameters used in the processesclassified as Type A, and the other parameters are used in the processesclassified as Type B. In addition, in FIG. 8 , the parameters labeled“O-RU Capability” indicate Capability information supported by the O-RU60. As the message specified in the NETCONF, an rpc message, anrpc-reply message, or a notification message is used, for example. TheO-DU 70 and the O-RU 60 use these messages to configure parameters(edit-config), to acquire parameters (get-config), or the like.

For example, the O-RU 60 and the FH-Proxy 50 configure MAC addressesdesignated in a Transport flow of “o-ran-processing element” of the Yangmodule. This defines the addresses of both ends of the flow definedbetween the O-RU 60 and the FH-Proxy 50. Each address can be a Sourceaddress and a Destination Address of data to be sent between the O-RU 60and the FH-Proxy 50. In addition, the O-DU 70 and the FH-Proxy 50similarly configure MAC addresses designated in the Transport flow of“o-ran-processing element” of the Yang module. This defines theaddresses of both ends of the flow defined between the O-RU 60 and theFH-Proxy 50. Each address can be a Source address and a DestinationAddress of data to be sent between the O-DU 70 and the FH-Proxy 50.

FIG. 9 shows a flow defined using address information designated in“o-ran-processing-element”. FIG. 9 shows that the FH-Proxy 50 isarranged between an O-RU 61, an O-RU 62, and an O-RU 63 and an O-DU 71,an O-DU 72, and an O-DU 73. Each of the number of O-DUs and the numberof O-RUs connected to the FH-Proxy 50 is not one, but multiple as shownin FIG. 9 , and the numbers of O-DUs and O-RUs may not be the same.

The FH-Proxy 50 defines an Address-1 of the O-DU 71 and an address-1A ofthe FH-Proxy 50 as a flow1 and communicates with the O-DU 71. The flowmay be referred to as a Transport flow. Similarly, the FH-Proxy 50defines an Address-2 of the O-DU 72 and an address-2A of the FH-Proxy 50as a flow2 and communicates with the O-DU 72. The FH-Proxy 50 defines anAddress-3 of the O-DU 73 and an address-3A of the FH-Proxy 50 as a flow3and communicates with the O-DU 73. The FH-Proxy 50 defines an Address-4of the O-RU 61 and an address-4A of the FH-Proxy 50 as a flow4 andcommunicates with the O-RU 61. The FH-Proxy 50 defines an Address-5 ofthe O-RU 62 and an address-5A of the FH-Proxy 50 as a flow5 andcommunicates with the O-RU 62. The FH-Proxy 50 defines an Address-6 ofthe O-RU 63 and an address-6A of the FH-Proxy 50 as a flow6 andcommunicates with the O-RU 63.

Since the number of O-DUs and the number of O-RUs connected to theFH-Proxy 50 are each multiple, the interconnectivity between any O-DUand any O-RU connected to the FH-Proxy 50 can be verified by configuringthe FH-Proxy 50 without physically plugging and unplugging the O-DUs andthe O-RUs.

When, for example, verifying the interconnectivity between the O-DU 71and the O-RU 61, the FH-Proxy 50 uses the Address-1A and the Address-4Afor the verification. In other words, when verifying theinterconnectivity between the O-DU 71 and the O-RU 61, the FH-Proxy 50uses the flow1 and the flow4 for the verification. Similarly, whenverifying the interconnectivity between the O-DU 72 and the O-RU 63, theFH-Proxy 50 uses the Address-2A and the Address-6A for the verification.

When performing a Type B process, the FH-Proxy 50 terminates andconverts the Transport Layer address as shown in FIG. 9 , but allows theNETCONF layer, which is an upper layer, to be transparent. The FH-Proxy50 records information transmitted in the NETCONF layer. In other words,the FH-Proxy 50 records information transmitted in the NETCONF layer asa log and visualizes the information transmitted in the NETCONF layer.In addition, when performing a Type A process, the FH-Proxy 50 recordsinformation transmitted in the NETCONF layer as a log and visualizes theinformation transmitted in the NETCONF layer.

Here, as an example of a process classified as Type B, a process relatedto “Retrieval of O-RU Information” is described with reference to FIG.10 . The process related to “Retrieval of O-RU Information” is a processto be performed by the O-DU 70 to acquire a parameter related to theO-RU 60. First, the O-DU 70 sends, to the FH-Proxy 50, a rpc message inwhich “get-config” for acquiring a parameter and “ru-id” indicating theparameter to be acquired are set (S11).

Next, the FH-Proxy 50 changes the Transport Layer address of thereceived rpc message (S12). Specifically, the FH-Proxy 50 changes thedestination MAC address of the rpc message to the MAC address of theO-RU 60 and changes the source MAC address to the MAC address of theFH-Proxy 50. When changing the Transport Layer address, the FH-Proxy 50changes “ietf-interface”, “o-ran-interface”, “o-ran-processing-element”used in the processes classified as Type A. Next, the FH-Proxy 50transfers, to the O-RU 60, the rpc message whose Transport Layer addresshas been changed (S13). At this time, the FH-Proxy 50 allows theinformation in the NETCONF layer of the rpc message to be transparent.

Next, the FH-Proxy 50 records the rpc message (S14). For example, theFH-Proxy 50 may record the header and payload of the rpc message.

Next, the O-RU 60 sends, to the FH-Proxy 50, a rpc-reply message inwhich, for example, “ru-id_A” is set as “ru-id” of the O-RU 60 (S15).

Next, the FH-Proxy 50 changes the Transport Layer address of thereceived rpc-reply message (S16). Specifically, the FH-Proxy 50 changesthe destination MAC address of the rpc-reply message to the MAC addressof the O-DU 70 and changes the source MAC address to the MAC address ofthe FH-Proxy 50. The parameters of the Yang module used to change theTransport Layer address are similar to those in step S12. Next, theFH-Proxy 50 transfers, to the O-DU 70, the rpc-reply message whoseTransport Layer address has been changed (S17).

Next, the FH-Proxy 50 records the rpc-reply message (S18). For example,the FH-Proxy 50 may record the header and payload of the rpc-replymessage. The FH-Proxy 50 records the header and payload of the rpc-replymessage, and thereby can record “ru-id_A” that is the information aboutthe O-RU 60 configured in the rpc-reply message as informationdesignated in the M-Plane.

In FIG. 10 , “Retrieval of O-RU Information” is described, but the O-DU70 may configure, in the rpc message, “edit-config” for configuring aparameter to configure the parameter to the O-RU 60 in other processes.

In FIG. 10 , the flow of data to be sent in the M-Plane is described,but the similar flow applies to data in the C-Plane, the U-Plane, andthe S-Plane. That is, the FH-Proxy 50 convers the Transport Layeraddress of data in the C-Plane, the U-Plane, and the S-Plane and recordsinformation to be sent in each layer.

As described above, the FH-Proxy 50 establishes an SSH connection witheach of the O-RU 60 and the O-DU 70 and configures each M-Plane, andthereby can record a message to be transferred in NETCONF. In otherwords, the FH-Proxy 50 can record the content set in the header andpayload of a message to be transferred in NETCONF. In addition, theFH-Proxy 50 can record messages of the C-Plane, the U-Plane, and theS-Plane that are not sent through the SSH connection.

In this manner, the FH-Proxy 50 can record messages related to theM-Plane, the C-Plane, the U-Plane, and the S-Plane. Accordingly, theadministrator or the like who manages the FH-Proxy 50 can use therecorded messages for an analysis process.

Third Example Embodiment

Next, a configuration example of an FH-Proxy 80 according to a thirdexample embodiment is described with reference to FIG. 11 . The FH-Proxy80 has a configuration in which a verification unit 81 is added to thecommunication apparatus 10 in FIG. 1 . The FH-Proxy 80 has aconfiguration in which the verification unit 81 that performs a messageanalysis process is added to the FH-Proxy 50 that records messagesrelated to the M-Plane, the C-Plane, the U-Plane, and the S-Plane. Inthe following, functions or processes of the FH-Proxy 80 that aredifferent from those of the FH-Proxy 50 corresponding to thecommunication apparatus 10 are mainly described.

A data recording unit 12 records, as data related to the M-Plane,Capability information about an O-RU 60, parameter values configured byan O-DU 70 to the O-RU 60, and the like, for example. In addition, thedata recording unit 12 records the header and payload in each layer of amessage related to each of the C-Plane, the U-Plane, and the S-Plane.The data recording unit 12 may convert the Transport Layer address ofthe message related to each of the C-Plane, the U-Plane, and the S-Planeand record the header and payload of each message when transferring it,similarly to the sequence in FIG. 10 .

The verification unit 81 uses various types of data recorded by the datarecording unit 12 to verify the interconnectivity between the O-RU 60and the O-DU 70. The verification unit 81 may autonomously performverification in accordance with a predetermined verification item. Forexample, the verification item may be to compare information designatedin the M-Plane with parameters of the C-Plane, the U-Plane, or theS-Plane configured based on the information. Alternatively, theverification item may be to display information sent and received in theM-plane in chronological order and check whether the information isprocessed in the order of FIG. 6 . The details of the interconnectivityverification are described below.

The data recording unit 12 records the Ethernet header of the messagerelated to each of the C-Plane and the U-Plane. FIG. 12 shows theEthernet header. Destination MAC Address and Source MAC Addresscontained in the Ethernet header are “o-du-mac-address” and“o-ru-mac-address” designated in the Transport flow of“o-ran-processing-element” of the M-Plane. In addition, “VLAN ID”contained in “VLAN Tag” contained in the Ethernet header is “vlan-id”designated in the Transport flow of “o-ran-processing-element” of theM-Plane. In addition, “CoS priority” contained in “VLAN Tag” is“u-plane-marking” and “c-plane-marking” designated in the M-Plane.

The verification unit 81 determines whether the information designatedin the M-Plane matches the information set in the Ethernet header. Whendetermining that they do not match, the verification unit 81 may output,to a display unit such as a display connected to the FH-Proxy 80, ananalysis result indicating that the information set in the Ethernetheader and the information designated in the M-Plane are differentvalues.

Next, the eCPRI Transport header is described with reference to FIG. 13. The data recording unit 12 records the eCPRI Transport headercontained in the Ethernet payload of the message related to the C-Plane.

Note that, “ecpriVersion” contained in the eCPRI Transport header is“ecpriVersion” contained in Capability information designated by theO-RU 60 in the M-Plane. In addition, “ecpriRtcid/ecpriPcid” is “eaxc-id”designated in the M-Plane.

The verification unit 81 determines whether the information designatedin the M-Plane matches the information set in the eCPRI Transportheader. When determining that they do not match, the verification unit81 may output, to a display unit such as a display connected to theFH-Proxy 80, an analysis result indicating that the information set inthe eCPRI Transport header and the information designated in the M-Planeare different values.

Then, a message specified as Section Type 1 in the Application layer ofthe C-Plane is described with reference to FIG. 14 . The data recordingunit 12 records a Section Type 1 message in the Application layer of theC-Plane.

The Section Type 1 message is a message to be sent from the O-DU 70 tothe O-RU 60 when the Capability information designated by the O-RU 60 inthe M-Plane indicates that the message is supported by the O-RU 60. Notethat, “symInc” contained in the Section Type 1 message is set to 1 whenthe Capability information designated by the O-RU 60 in the M-Planeindicates the parameter is supported by the O-RU 60. In addition,“beamID” is “Beam id” contained in the Capability information designatedby the O-RU 60 in the M-Plane. In addition, “udCompHdr” is set based onCompression method contained in the Capability information designated bythe O-RU 60 in the M-Plane.

The verification unit 81 determines whether the information designatedin the M-Plane matches the information set in the Section Type 1message. Alternatively, the verification unit 81 may determine whetherinformation to be set based on the information designated in the M-Planematches the information set in the Section Type 1 message. Whendetermining that they do not match, the verification unit 81 may output,to a display unit such as a display connected to the FH-Proxy 80, ananalysis result indicating that the information set in the Section Type1 message and the information designated in the M-Plane are differentvalues.

Next, a message specified as Section Type 3 in the Application layer ofthe C-Plane is described with reference to FIG. 15 . The data recordingunit 12 records a Section Type 3 message in the Application layer of theC-Plane.

The Section Type 3 message is a message to be sent from the O-DU 70 tothe O-RU 60 when the Capability information designated by the O-RU 60 inthe M-Plane indicates that the message is supported by the O-RU 60.“Frame structure” contained in the Section Type 3 message is the valueindicated in the Capability information designated by the O-RU 60 in theM-Plane. Note that, “symInc” is set to 1 when the Capability informationdesignated by the O-RU 60 in the M-Plane indicates that the parameter issupported by the O-RU 60. In addition, “beamID” is “Beam id” containedin the Capability information designated by the O-RU 60 in the M-Plane.In addition, “udCompHdr” is set based on Compression method contained inthe Capability information designated by the O-RU 60 in the M-Plane.

The verification unit 81 determines whether the information designatedin the M-Plane matches the information set in the Section Type 3message. Alternatively, the verification unit 81 may determine whetherinformation to be set based on the information designated in the M-Planematches the information set in the Section Type 3 message. Whendetermining that they do not match, the verification unit 81 may output,to a display unit such as a display connected to the FH-Proxy 80, ananalysis result indicating that the information set in the Section Type3 message and the information designated in the M-Plane are differentvalues.

Next, a message specified as Section Type 1 and 3 in the Applicationlayer of the U-Plane is described with reference to FIG. 16 . The datarecording unit 12 records a Section Type 1 and 3 message in theApplication layer of the U-Plane.

The Section Type 3 message is a message to be sent from the O-DU 70 tothe O-RU 60 when the Capability information designated by the O-RU 60 inthe M-Plane indicates that the message is supported by the O-RU 60. Notethat, “symInc” contained in the Section Type 1 and 3 message is set to 1when the Capability information designated by the O-RU 60 in the M-Planeindicates that the parameter is supported by the O-RU 60. In addition,“udCompHdr” is set based on Compression method contained in theCapability information designated by the O-RU 60 in the M-Plane.

The verification unit 81 determines whether the information designatedin the M-Plane matches the information set in the Section Type 1 and 3message. Alternatively, the verification unit 81 may determine whetherinformation to be set based on the information designated in the M-Planematches the information set in the Section Type 1 and 3 message. Whendetermining that they do not match, the verification unit 81 may output,to a display unit such as a display connected to the FH-Proxy 80, ananalysis result indicating that the information set in the Section Type1 and 3 message and the information designated in the M-Plane aredifferent values.

As described above, the FH-Proxy 80 analyzes the message recorded by thedata recording unit 12 to determine whether the information designatedin the M-Plane matches the information set in the C-Plane and theU-Plane. Accordingly, the FH-Proxy 80 can determine whether theinformation designated in the M-Plane is correctly set to data to besent from the O-RU 60 or the O-DU 70. In addition, when it is determinedthat the information designated in the M-Plane is not correctly set, theadministrator or the like of the FH-Proxy 80 can analyze theconfiguration of the O-RU 60 or the O-DU 70 that is the source of themessage to determine which apparatus has a problem. Alternatively, theFH-Proxy 80 may autonomously analyze which apparatus has a problem inaccordance with a predetermined scenario. In addition, messages that canbe analyzed by the verification unit 81 are not limited to the abovemessages.

Modified Example in Second and Third Example Embodiments

In the second example embodiment, it has been described that theFH-Proxy 50 or the FH-Proxy 80 is arranged between the O-RU 60 and theO-DU 70, and the FH-Proxy 50 or FH-Proxy 80 acquires a message to betransmitted between the O-RU 60 and the O-DU 70. In contrast, anFH-Proxy 100 may be arranged between the O-RU 60 and an NMS 90 as shownin FIG. 17 , and the FH-Proxy 100 may acquire a message to betransmitted between the O-RU 60 and the NMS 90. The O-DU 70 in FIG. 17controls a part of parameters or functions of the O-RU 60, and the NMS90 controls the rest of the parameters or functions. Any of nodes suchas a network switch, a bridge, a router, and a Fronthaul Multiplexerconnected between the O-RU 60 and the O-DU 70 or the NMS 90 may beequipped with all or a part of the communication unit, the datarecording unit, and the verification unit of the FH-Proxy 80.

FIG. 18 is a block diagram showing a configuration example of thecommunication apparatus 10, the FH-Proxy 50, the FH-Proxy 80, and theFH-Proxy 100 (hereinafter, referred to as the communication apparatus 10or the like). In FIG. 18 , the communication apparatus 10 or the likeincludes a network interface 1201, a processor 1202, and a memory 1203.The network interface 1201 is used to communicate with a network node(e.g., eNB, MME, P-GW). The network interface 1201 may include, forexample, a network interface card (NIC) in compliance with the IEEE802.3 series. Here, eNB represents evolved Node B, MME representsMobility Management Entity, and P-GW represents Packet Data NetworkGateway. IEEE represents Institute of Electrical and ElectronicsEngineers.

The processor 1202 loads software (a computer program) from the memory1203 and executes it to perform the processes of the communicationapparatus 10 or the like that are described with reference to theflowchart in the above example embodiments. The processor 1202 may be,for example, microprocessor, an MPU or a CPU. The processor 1202 mayinclude a plurality of processors.

The memory 1203 is configured by a combination of a volatile memory anda non-volatile memory. The memory 1203 may include a storage arrangedaway from the processor 1202. In this case, the processor 1202 mayaccess the memory 1203 via an Input/Output (I/O) interface that is notillustrated.

In the example in FIG. 18 , the memory 1203 is used to store a group ofsoftware modules. The processor 1202 loads the group of software modulesfrom the memory 1203 and executes them to perform the processes of thecommunication apparatus 10 or the like described in the above exampleembodiments.

As described with reference to FIG. 18 , each processor included in thecommunication apparatus 10 or the like in the above example embodimentsexecutes one or more programs containing a set of instructions forcausing a computer to execute the algorithms described with reference tothe drawings.

In the above examples, the one or more programs can be stored by varioustypes of non-transitory computer-readable media and provided to acomputer. Non-transitory computer-readable media include any type oftangible storage media. Examples of non-transitory computer-readablemedia include magnetic storage media (such as flexible disks, magnetictapes, and hard disk drives), optical magnetic storage media (such asmagneto-optical disks), Compact Disc Read Only Memory (CD-ROM), CD-R,CD-R/W, and semiconductor memories (such as mask ROM, Programmable ROM(PROM), Erasable PROM (EPROM), flash ROM, and Random Access Memory(RAM)). The one or more programs may be provided to a computer using anytype of transitory computer-readable media. Examples of transitorycomputer-readable media include electric signals, optical signals, andelectromagnetic waves. Transitory computer readable media can providethe one or more programs to a computer through a wired communicationline (such as electric wires, and optical fibers) or a wirelesscommunication line.

The present invention has been described above with reference to theexample embodiments but is not limited by the above. Variousmodifications that can be understood by those skilled in the art can bemade to the configurations and the details of the present inventionwithin the scope of the invention.

Note that, the present disclosure is not limited to the above exampleembodiments and can be modified without departing from the gist thereof.

This application is based upon and claims the benefit of priority ofJapanese Patent Application No. 2020-042467 filed on Mar. 11, 2020, thedisclosure of which is incorporated herein in its entirety by reference.

A part or all of the above example embodiments may be described as thefollowing Supplementary notes but are not limited to the following.

(Supplementary Note 1)

A communication apparatus comprising:

a communication means for establishing a first Secure Shell (SSH)connection with a wireless apparatus configured to perform wirelesscommunication with a communication terminal and for establishing asecond SSH connection with a control apparatus configured to perform abaseband process related to a signal used in the wireless communication;and

a data recording means for recording data of a management plane receivedfrom the wireless apparatus through the first SSH connection or the dataof the management plane received from the control apparatus through thesecond SSH connection.

(Supplementary Note 2)

The communication apparatus according to Supplementary note 1, whereinthe communication means changes a destination address of first data ofthe management plane received from the wireless apparatus to a firstaddress indicating the control apparatus to send the first data to thecontrol apparatus, and changes a destination address of second data ofthe management plane received from the control apparatus to a secondaddress indicating the wireless apparatus to send the second data to thewireless apparatus.

(Supplementary Note 3)

The communication apparatus according to Supplementary note 2, whereinthe communication means changes a source address of the first data to besent to the control apparatus to a third address indicating thecommunication apparatus, and changes a source address of the second datato be sent to the wireless apparatus to a fourth address indicating thecommunication apparatus.

(Supplementary Note 4)

The communication apparatus according to Supplementary note 2 or 3,wherein an address to be set for each of the first data and the seconddata is a Media Access Control (MAC) address.

(Supplementary Note 5)

The communication apparatus according to any one of Supplementary notes1 to 4, wherein

the communication means acquires data of at least one of a controlplane, a user plane, or a synchronization plane to be sent between thewireless apparatus and the control apparatus, and

a destination address to be set for the acquired data is specified usingthe data of the management plane.

(Supplementary Note 6)

The communication apparatus according to any one of Supplementary notes1 to 5, wherein the data recording means records the data of at leastone of the control plane, the user plane, or the synchronization planereceived from the wireless apparatus or the control apparatus, and

the communication apparatus further includes a verification means fordetermining, using the data of the management plane, whether correctinformation is set for the data of at least one of the control plane,the user plane, or the synchronization plane.

(Supplementary Note 7)

A data recording method comprising:

establishing a first Secure Shell (SSH) connection with a wirelessapparatus configured to perform wireless communication with acommunication terminal;

establishing a second SSH connection with a control apparatus configuredto perform a baseband process related to a signal used in the wirelesscommunication; and

recording data of a management plane received from the wirelessapparatus through the first SSH connection or the data of the managementplane received from the control apparatus through the second SSHconnection.

(Supplementary Note 8)

A non-transitory computer-readable medium storing a program causing acomputer to execute:

establishing a first Secure Shell (SSH) connection with a wirelessapparatus configured to perform wireless communication with acommunication terminal;

establishing a second SSH connection with a control apparatus configuredto perform a baseband process related to a signal used in the wirelesscommunication; and

recording data of a management plane received from the wirelessapparatus through the first SSH connection or the data of the managementplane received from the control apparatus through the second SSHconnection.

REFERENCE SIGNS LIST

-   10 Communication apparatus-   11 Communication unit-   12 Data recording unit-   20 Wireless apparatus-   30 Control apparatus-   40 Communication terminal-   50 FH-Proxy-   60 O-RU-   61 O-RU-   62 O-RU-   63 O-RU-   70 O-DU-   71 O-DU-   72 O-DU-   73 O-DU-   80 FH-Proxy-   81 Verification unit-   90 NMS-   100 FH-Proxy

1. A communication apparatus comprising: a communication means forestablishing a first Secure Shell (SSH) connection with a wirelessapparatus configured to perform wireless communication with acommunication terminal and for establishing a second SSH connection witha control apparatus configured to perform a baseband process related toa signal used in the wireless communication; and a data recording meansfor recording data of a management plane received from the wirelessapparatus through the first SSH connection or the data of the managementplane received from the control apparatus through the second SSHconnection.
 2. The communication apparatus according to claim 1, whereinthe communication means is configured to change a destination address offirst data of the management plane received from the wireless apparatusto a first address indicating the control apparatus to send the firstdata to the control apparatus, and change a destination address ofsecond data of the management plane received from the control apparatusto a second address indicating the wireless apparatus to send the seconddata to the wireless apparatus.
 3. The communication apparatus accordingto claim 2, wherein the communication means is configured to change asource address of the first data to be sent to the control apparatus toa third address indicating the communication apparatus, and change asource address of the second data to be sent to the wireless apparatusto a fourth address indicating the communication apparatus.
 4. Thecommunication apparatus according to claim 2 or 3, wherein an address tobe set for each of the first data and the second data is a Media AccessControl (MAC) address.
 5. The communication apparatus according to anyone of claims 1 to 4, wherein the communication means is configured toacquire data of at least one of a control plane, a user plane, or asynchronization plane to be sent between the wireless apparatus and thecontrol apparatus, and a destination address to be set for the acquireddata is specified using the data of the management plane.
 6. Thecommunication apparatus according to any one of claims 1 to 5, whereinthe data recording means is configured to record the data of at leastone of the control plane, the user plane, or the synchronization planereceived from the wireless apparatus or the control apparatus, and thecommunication apparatus further includes a verification means fordetermining, using the data of the management plane, whether correctinformation is set for the data of at least one of the control plane,the user plane, or the synchronization plane.
 7. A data recording methodcomprising: establishing a first Secure Shell (SSH) connection with awireless apparatus configured to perform wireless communication with acommunication terminal; establishing a second SSH connection with acontrol apparatus configured to perform a baseband process related to asignal used in the wireless communication; and recording data of amanagement plane received from the wireless apparatus through the firstSSH connection or the data of the management plane received from thecontrol apparatus through the second SSH connection.
 8. A non-transitorycomputer-readable medium storing a program causing a computer toexecute: establishing a first Secure Shell (SSH) connection with awireless apparatus configured to perform wireless communication with acommunication terminal; establishing a second SSH connection with acontrol apparatus configured to perform a baseband process related to asignal used in the wireless communication; and recording data of amanagement plane received from the wireless apparatus through the firstSSH connection or the data of the management plane received from thecontrol apparatus through the second SSH connection.